An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

My app review is pending for 20 days now, when will that happen?

Hello everyone, I'm an independent developer trying to release my first iOS app, Somnolia. I've already gone through three previous App Review rejections, each concerning a different issue. I carefully addressed the feedback provided by Apple and submitted an updated build on October 14, 2026. Unfortunately, my fourth submission has now been stuck in "Waiting for Review" for 17 days, without any progress or additional communication. Submission details: App: Somnolia Apple App ID: 6794948071 Version: 1.0 (Build 6) Submission date: October 14, 2026 Current status: Waiting for Review I've already contacted Apple Developer Support by phone and opened another support case today, October 31, but I still don't know why the review hasn't started. I completely understand that Apple needs time to review applications, especially after previous rejections. However, I've addressed three separate issues, and I'm concerned that my submission might be stuck in the review queue. Has anyone experienced a similar situation recently? If someone from Apple sees this post, I would really appreciate any guidance on whether my submission is correctly queued or if any further action is needed on my side. I've spent months developing this application independently, and I would simply like to understand what's happening. Thank you for your help!

Hello App Review team and fellow developers, Our app Quotio – Quotes & Invoices (Apple ID 6776653813, iOS 1.0.1, build 15) has been in "Waiting for Review" since October 13, 2026. We resubmitted it with a new build on October 27, and it has been waiting again since then, with no status change and no message in App Store Connect. This is our first release. The app is free, has no in-app purchases, and is already used by external testers through TestFlight. We have accepted the latest agreements, opened a support case (103014927310) and requested an expedited review, which was accepted. Is there anything we can check on our side? Thank you!

Apple, Please Investigate: Two Apps Rejected for Information Already Provided in the Original Submissions Dear Apple Developer Community and App Review Team, I am writing to report a serious and extremely frustrating problem I have experienced with two different applications submitted to the App Store. Both applications were rejected under App Review Guideline 1.3, requesting answers to four questions that I had already answered completely in the App Review Notes during the ORIGINAL submissions. The information was not added after rejection. It was already provided before either application entered review. I fully support Apple’s strict requirements for children’s applications. However, these repeated incidents raise serious concerns about how App Review Notes and supporting documents are handled. **1. Kalimati - كلماتي Apple App ID: 6812125263** Kalimati is an educational application that helps children learn Arabic words and action verbs through interactive activities and animations. When submitting Kalimati for the first time, I explicitly answered all four required questions in the App Review Notes: Third-party analytics. Third-party advertising. Sharing user or device data with third parties. Other collection or processing of user or device information. Despite providing complete answers, Kalimati was rejected on October 11, 2026, requesting answers to those exact same questions. These answers were already included in the original submission! I responded again and resubmitted the application on October 11. As of October 22, Kalimati remains in “Waiting for Review” status, 11 days after resubmission. I contacted Apple Developer Support multiple times. Although I was informed that steps would be taken to expedite the review, the application remains in the queue. This delay followed a request for information that had already been provided. **2. HeroHop: Sky Adventure Apple App ID: 6823625184** After my experience with Kalimati, I took additional precautions before submitting HeroHop on October 20, 2026. I provided the answers in TWO separate places: First: Complete answers to all four questions in the App Review Notes. Second: A detailed two-page PDF attachment titled “HeroHop-App-Review-Notes-Build-8.pdf”, addressing each question individually and explaining privacy practices, data handling, parental controls, and in-app purchases. Nevertheless, HeroHop was rejected the following day with an automated message requesting answers to the exact same four questions! I had answered every question in the designated field AND attached detailed supporting documentation. Yet the application was rejected as though none of this information had been provided. I repeated the answers and resubmitted HeroHop on October 21. The Real Problem The issue is not Apple’s requirement to answer privacy-related questions. Those questions are reasonable and important. The issue is that Apple repeatedly requests information that developers have ALREADY provided in the designated submission fields. With Kalimati, the answers were included in App Review Notes. With HeroHop, the answers were included in App Review Notes AND a separate PDF. Both applications received requests for the same information again. This raises important questions: Are App Review Notes displayed correctly to reviewers? Are supporting documents properly accessible? Are automated requests generated without checking existing answers? Is there a procedural problem in reviewing Kids Category submissions? I cannot determine the cause from outside Apple’s systems. However, experiencing the same issue twice, despite taking additional precautions, strongly suggests that the submission or review workflow requires investigation. The Consequences for Developers Every unnecessary rejection can delay an application for days or weeks. Kalimati has remained in “Waiting for Review” since October 11. Developers spend considerable time preparing applications, testing them, documenting compliance, and answering Apple’s questions. It is extremely frustrating to complete these requirements correctly, only to receive a rejection requesting information that was already provided. This wastes developers’ time, disrupts release schedules, and undermines confidence in Apple’s review process. What Apple Should Investigate and Improve I respectfully urge Apple’s App Review management and App Store Connect teams to investigate and improve the following: 1. Verify App Review Notes: Ensure submitted information is correctly stored, displayed, and examined before requesting additional answers. 2. Verify attachments: Ensure supporting PDFs and documents are clearly visible and accessible to reviewers. 3. Prevent repeated requests: Before issuing a rejection, verify whether the requested information already exists in the original submission. 4. Provide specific explanations: If an answer is insufficient, explain precisely what is missing instead of repeating the same questionnaire. 5. Investigate the Kids Category workflow: Examine why the same four Guideline 1.3 questions are repeatedly requested despite documented answers. 6. Establish an escalation channel: Allow developers to report recurring procedural problems beyond individual rejection decisions. Concern About My Upcoming macOS Application I am currently developing another application for macOS. After these experiences, I am genuinely concerned that I may encounter another unnecessary rejection because information I carefully provide is overlooked. Developers should not have to worry whether their App Review Notes will actually be considered. A Direct Appeal to Apple I am not requesting special treatment, exceptions to Apple’s guidelines, or approval without proper review. I fully respect Apple’s responsibility to protect users, particularly children. I am simply asking Apple to ensure that information developers provide is actually read and considered before applications are rejected for supposedly missing information. Apple, please investigate this issue at both the management and technical levels. If there is a technical problem, fix it. If there is a procedural problem, improve the procedure. If answers are insufficient, explain exactly what is missing. This is a real and recurring problem that deserves serious attention. I also invite fellow developers to share their experiences: Have you received a Guideline 1.3 rejection requesting the four Kids Category answers even though you had already provided them in your original App Review Notes? I sincerely hope Apple takes this issue seriously and investigates its underlying cause. A Final Request to the Community Please help bring this issue to Apple’s attention. Salman Farhat

Hello, I’m an independent developer and founder of a startup preparing for its first App Store launch. Our application was rejected under Guideline 4.3(a) for alleged similarity to other applications. We believe the rejection may be related to an earlier version of our own application that existed exclusively for internal TestFlight testing under a different developer account. That version was never submitted for public App Store review. We provided a detailed explanation to App Review and resubmitted the application without code changes, as we dispute the original finding. Our current submission has now remained in “Waiting for Review” for over 60 hours. We have already requested expedited review and opened a Developer Support case, but have received no substantive response. Our business launch is time-sensitive, and the continued uncertainty is causing significant financial and operational difficulties. Could an Apple App Review representative please advise whether there is a way to escalate this matter or arrange private communication with the appropriate team? I would be happy to provide our App ID, Submission ID, support case number and supporting documentation privately through an official Apple channel. Thank you.

Hi, I am a solo developer with an individual account since 2024. I would appreciate guidance from App Review, because I do not know what else I can do from my side. On October 13 at 00:06 all five apps I had in review were rejected within the same minute under 4.3 and 4.2.6, each with the same nine questions about the app, its audience, beta testing, shared code and templates. The apps are not related: a voice recorder with on-device transcription, a dice roguelike, a tile based dungeon game, a studio simulation game and a Safari extension for cookie banners. I built them myself in Xcode over several weeks and submitted each one when it was finished, which is why they arrived in the same week. No template, no generation service, no client, no third party SDKs, no other accounts. The same day I answered all nine questions in full for four of the apps and withdrew the fifth, the cookie banner extension, to rebuild it. Nine days later there is no response on any of the four threads. On October 21 I submitted the rebuilt extension as version 2.0. It now has consent receipts decoded from each site's TCF record, a public page listing the 100 sites tested before every release with the result for each, a separate mode for subscribe-or-consent walls, Global Privacy Control, Shortcuts and a Mac app. A review video and a public test page were attached. It was rejected within a day under 4.3(a) as sharing "a similar binary, metadata and/or concept" with apps submitted by me or others, with an Extended Review note. The only earlier app with this name is my own withdrawn 1.0. I have stopped submitting anything. My questions: Is there anything more I can provide for the four open threads so a reviewer can look at the apps themselves? I can send screen recordings, source code or demo builds the same day. For the 4.3(a) rejection: what was the app matched against, and what counts as a sufficient difference in this category, given that several cookie banner blockers for Safari were approved in 2026? App IDs: 6821429432 (Voice Notes: Local Transcribe), 6821423492 (Lampfall), 6821275353 (Bone Caster), 6819040142 (Vibe Coder), 6818993189 (Cookie Hide, version 2.0). Thank you for your time. Armen Ter-Oganezov

I am looking for guidance from Apple or other developers who have experienced a similar Guideline 4.3(a) rejection. I submitted an independently developed iPhone/iPad application, Canvasz AI: Passport ID Photo, for App Review. On September 30, 2026, the app was rejected under Guideline 4.3(a) – Design – Spam, with a general statement that the app appeared to share a similar binary, metadata, and/or concept with apps submitted by other developers. The problem is that I have not been able to determine what Apple actually considers similar. Canvasz AI was developed independently and was not created from a purchased template, white-label application, cloned application, or repackaged source code. The application includes product-specific functionality such as: Real-time face-position and distance guidance before taking a photo On-device face detection and format-aware automatic framing Passport/document head-size framing logic On-device background segmentation, matting, and replacement without uploading the user's photo to a processing server One source photo converted into multiple destination classes, including passport/visa/ID photos, profile images, social-media formats, and banners Batch generation/export of supported formats from one source photo An enhancement pipeline intended to preserve facial detail rather than apply a generic beauty filter Seven localized languages iPhone and iPad layouts Portrait and landscape support No account or signup requirement Core photo processing that works locally/on-device Following the rejection, I replied through App Store Connect asking whether the concern related specifically to: Binary/source-code similarity Metadata Visual assets/UI The application concept itself I also performed an additional source-provenance and similarity audit. The audit documented progressive source-control history and compared Canvasz AI against my other independently developed applications. It found no byte-identical application-specific source/assets across the compared applications, the common files identified were normal Flutter/iOS/Android generated framework/scaffolding files. I attached the forensic technical clarification report to App Review and offered to provide source-control history, architecture information, screenshots, development evidence, or additional technical information if required. I first replied on September 30 and followed up again on October 5. I still did not receive clarification identifying the actual similarity concern. I subsequently resubmitted the application on October 12, 2026, with detailed App Review notes and the forensic report attached. As of October 25, 2026, both the app and its in-app purchase remain Waiting for Review. I understand that App Review may require additional time, especially after a previous Guideline 4.3 rejection. I am not asking for special treatment or asking Apple to disclose another developer's confidential application or internal detection systems. What I need is enough actionable information to understand how to comply. Apple's published Guideline 4.3 states that apps in established categories may be accepted when they provide a meaningfully different or improved experience. I therefore have three specific questions: If an independently developed application receives a 4.3(a) rejection referring to "binary, metadata, and/or concept," how can the developer determine which of those dimensions actually caused the rejection? If source provenance and independent development evidence are provided, but no clarification is received, what additional evidence is normally useful for demonstrating that an application is not a template, clone, or repackaged application? For the "meaningfully different or improved experience" standard, should differentiation be evaluated on the complete user workflow and experience, or is overlap in individual features sufficient to trigger Guideline 4.3? I have invested significant development, testing, localization, and product-design effort into building a genuine application intended to provide useful functionality to users. I fully respect Apple's need to prevent spam, cloned apps, white-label applications, and low-effort template submissions. I support that objective. However, without knowing whether the concern is source code, metadata, UI/assets, or the concept itself, it is extremely difficult for an independent developer to make a meaningful correction instead of making speculative changes. I would appreciate guidance from Apple or developers who have encountered this situation and successfully obtained actionable clarification. Thank you.

Hello, Our app Profik Pro (Apple ID 6787445540) was submitted for review on October 10, 2026: version 1.1.14 together with its first four in-app purchase products. The expedited review was confirmed right away ("We'll expedite review for Profik Pro"), and again when I re-requested it on October 15. The submission is still in "Waiting for Review" and has never moved to "In Review". What we have checked: All agreements are Active. We accepted the updated Apple Developer Program License Agreement and Paid Applications Schedule on October 13; banking and tax forms are active too. There are no messages from App Review and nothing marked as action required in App Store Connect. Our other app (Profik, Apple ID 6759965214) was submitted on October 13, reviewed and approved within a day. We also opened a Developer Support case (102995482417) on October 13 and added the details above, but haven't heard back yet. Phone support currently shows as unavailable. Is there anything else we can check on our side, for example something about first-time in-app purchases that could hold a submission? Has anyone seen a submission stay in the expedited queue this long? Thank you!

Hello App Review team and fellow developers, Our Padel Tempo: Padel Score iOS 1.0 submission has been in Waiting for Review for nearly five days after a metadata-only resubmission, and I would like to make sure that nothing else is required from our side. App: Padel Tempo: Padel ScoreVersion: iOS 1.0Submission ID: cbc83032-2f7a-4f80-bc2c-e54a5c9f68b3Resubmitted: October 26, 2026 at 5:04 PMCurrent status: Waiting for Review What happened Our initial submission was reviewed on October 26. We received an automated App Review message regarding the auto-renewable subscriptions Premium Monthly and Premium Yearly. The only issue identified was a missing functional link to the standard Apple Terms of Use (EULA) in the App Store metadata. We corrected the issue immediately: added the standard Apple Terms of Use (EULA) link to the App Description; made sure the required metadata was complete; no binary changes were necessary; resubmitted the same app version approximately 12 minutes after receiving the review message. Since then, the submission has remained in Waiting for Review. Why I am posting I understand that review times can vary, and I am not asking to skip the queue. I would simply like to confirm that: the resubmission is correctly queued for App Review; the previous metadata issue is considered resolved; no additional action or information is currently required from us. Since this was a metadata-only correction following an already completed first review, I wanted to make sure the resubmission did not end up waiting because of something we may have missed. If App Review needs any additional information, screenshots, test instructions, or clarification, I can provide it immediately. Thank you for your time, and I would also appreciate hearing from other developers who have recently experienced longer-than-usual Waiting for Review times. Best regards,MykolaPadel Tempo

I submitted my app for App Store Review on 27th October 2026. As of 31st October 2026, it has been approximately 4 days, and the app's status in App Store Connect is still showing "Waiting for Review". It has not yet moved to "In Review". I'm using an Individual Apple Developer Account. I have already contacted Apple Developer Support and raised a support ticket regarding this delay. I'd like to hear from other developers: Are Individual Developer accounts experiencing longer review wait times compared to Organization accounts? Has anyone else submitted an app recently and experienced a similar delay? How long did it take for your app to move from "Waiting for Review" to "In Review"? Is there anything else I should do while waiting for Apple's response? Any recent experiences or suggestions would be greatly appreciated. Thanks!

I first put my app on review the 25th of September. After four days, I thought something was wrong so I resubmitted it 29th of September. I then learnt that was not the case. I sent a couple of emails to ask what was happening and after a long while 7 days maybe) I got a reply that my app was now expedited. On the 15th of October it had been reviewed with a rejection and a somewhat minor thing I needed to fix. I did that and resubmitted the 17th of October. It should still be expedited, as per the comms. I am now, the 29th of October still waiting. What is going on? this is the Apple ID: 6803645894

Hello everyone, and happy Halloween! I’m looking for advice on how to handle an App Store Review deadlock. The Issue: Our app is new. It was initially rejected with a few required changes. We addressed the feedback on the same day and submitted a new build each time. However, whenever a rejection occurs (showing the red exclamation mark next to "App Review"), the submission seems to enter a deadlock state with zero progress. To break out of this, we had to manually cancel/reject the build twice and resubmit a new version. Up until now, our review expedites were processed within 48 hours. Current Situation: The latest review has now been completely stuck for over a week. Submitted an Expedited Review request → No response. Contacted Developer Support → No response. Why it's critical: We have scheduled external press and interviews going live that cannot be postponed, and we risk losing potential users if the app isn't live on the App Store in time. Has anyone experienced a similar deadlock after resolving a rejection? Is there any effective way to escalate this with Apple Developer Relations when support form inquiries go unanswered? Any advice or insights would be greatly appreciated! Apple-ID 6821089281

Hi everyone, After my app was rejected, repeated contact attempts and an appeal have not led to any meaningful guidance. What should I do next? Apple ID: 6807882674 Review timeline (all dates are in 2026): September 7: First submitted the app for App Store review. September 16: The app was rejected. I then sent three messages through Contact Us and received no reply to any of them. I subsequently submitted an appeal, which also received no response. During this period: I continued developing the app, updating the review information and resubmitting. Multiple TestFlight external beta builds were also rejected. When I contacted Apple about those rejections, the replies were generic process information with no specific advice on what to change. October 20 (UTC): Resubmitted the app for App Store review. As of October 27, it is still Waiting for Review, with no further update. It has been 50 days since my first submission, including rejection, an appeal and resubmissions. I understand that reviews take time. However, the replies I have received feel mechanical and unhelpful: they repeat general process information without addressing my specific questions or explaining what needs to change. I still do not know how to move forward. Has anyone experienced a similar situation? How can I obtain case-specific guidance? If an Apple staff member sees this, could you help check my case or advise on the next step? I can provide the relevant case numbers through the support channel. Thank you for your help. I will update this thread daily until there is substantive progress with the review.

I'm genuinely at a loss with Apple's App Review process. Our backend records show that across BOTH reviews, Apple's reviewers did not complete a SINGLE use of our app's core functionality. Not once. ZERO completed generations. For the latest review, our logs confirm Apple successfully logged in, but recorded ZERO generation requests and ZERO credits consumed. This isn't some minor feature. It's the entire foundation of our app. Our app fundamentally changes and becomes personalised as it's used. Without completing that process, you're essentially judging an incomplete product. Submission ID: 6a126514-9bb6-4d91-923c-bf29aacb1b68 Here's why this is so frustrating. We spent months deliberately building an app that offers functionality and a user experience fundamentally different from existing competitors. This wasn't another copycat app - avoiding that was central to its design from day one. We explained these differences extensively in our App Review notes. Yet Apple has rejected us TWICE under Guideline 4.3(b) — Design Spam. We even provided a narrated walkthrough demonstrating exactly what makes our app unique. Our video analytics show ZERO views. So we're being rejected for supposedly lacking originality, despite neither review producing a completed use of our main feature and no recorded views of our demonstration. After both rejections, we've received nothing but generic responses telling us to improve the app, without identifying a single specific problem. How are independent developers supposed to fix something when Apple won't explain what's wrong? We've now filed a formal appeal, which could take a month, with no visible queue position, progress updates or estimated timeframe. Meanwhile, we've already missed multiple planned marketing opportunities, and waiting could mean missing even more. We're not asking for guaranteed approval. We're asking for a fair review of what we've actually built. Has anyone else experienced this? What would you do? Wait for the appeal, hoping the App Review Board properly evaluates the app, even if it takes another month and we miss more deadlines? Withdraw the appeal and resubmit, hoping for a different reviewer, but risking another rejection without proper testing and further warnings against our developer account? I'd genuinely appreciate advice from anyone who's experienced something similar, especially those who've successfully appealed a 4.3(b) rejection. At this point, I genuinely don't know whether this is a reviewer misunderstanding, an automated rejection process, or something else entirely. But how can Apple determine that an app lacks originality when its defining functionality hasn't even been tested?

Hi all, I'm looking for guidance on getting my app back on sale. I've done everything I know to do and I'm not sure what step I'm missing. Details below. Timeline: Aug 16: The app was removed from sale through App Store Notices (ref APP265997). Sept: I renamed the app with a new name, icon, and listing, which was the agreed resolution. Oct 2: Apple lifted the submission hold. Oct 5: The other party confirmed to App Store Notices that the matter is closed and the app can be restored. Oct 7: Version 1.0.4 was approved. App Store Connect shows it as "Ready for Distribution," but the version page also shows a banner: "This app was removed from sale from the App Store." The product page returns "can't be found." I've accepted all current agreements. Oct 20: I submitted 1.0.5 (Manual release). It has been in "Waiting for Review" for 8 days and hasn't moved to In Review. Oct 23: I followed up with App Store Notices and have not heard back yet. My questions: Once an App Store Notices matter is closed, is there a separate step to restore the app to sale, or does App Store Notices lift the removal on their end? Could the removal be why 1.0.5 hasn't entered review after 8 days? Is there a better contact or channel for this than the App Store Notices thread? Any guidance from Apple staff or anyone who has been through this would be a huge help. Existing users can't get the latest fixes, and new users can't find the app at all. Thank you.

Hi Apple Developer Community, I'm reaching out to share my situation and seek advice from developers who may have experienced something similar. Recently, my Apple Developer account received a Pending Termination Notice, and my app, FastWise: IF Fasting Timer (App ID: 6798288587), was removed from the App Store. Apple stated that the account had been flagged for alleged dishonest or fraudulent activity related to developer identity or account information, citing Section 3.2(f) of the Apple Developer Program License Agreement and App Review Guideline 5.6.2. I submitted an official appeal to the App Review Board on October 8, 2026, explaining my situation and requesting a review of the decision. I also contacted Apple Developer Support by phone. However, as of October 16, I have not received any updates or response regarding my appeal. I'm concerned because the notice states that my developer membership may be terminated, earnings payments are paused, and app transfers are disabled. I fully respect Apple's policies and understand the importance of maintaining a trustworthy App Store ecosystem. I am willing to provide any additional information or documentation required to resolve this matter. I would appreciate guidance from the community on a few questions: Has anyone experienced a similar Pending Termination Notice and successfully appealed it? How long does Apple typically take to respond to a developer account termination appeal? Is there an official way to request a status update or escalation when an appeal has already been submitted? Are there any additional steps I should take while waiting for the App Review Board's response? App: FastWise: IF Fasting Timer App ID: 6798288587 Appeal submitted: October 8, 2026 Any insights or experiences would be greatly appreciated. I hope to resolve this situation fairly and continue developing apps for the Apple ecosystem. Thank you for your support!

Hello everyone, We submitted a major update for our social networking app, Yuppi, on October 23, 2026. Both our TestFlight and App Store submissions are still in "Waiting for Review" status. Following a previous consultation with Apple's App Review team, we carefully addressed their feedback, completely redesigned our app, and introduced several new features. We fully understand and respect Apple's review procedures and standard timelines. However, our main priority at this stage is TestFlight. We would love to give our existing users the opportunity to experience and test our new design and features before the official App Store release. We completely understand that the App Store review may take additional time, and we have no concerns about following the standard process. We would sincerely appreciate any guidance from the Apple App Review team regarding whether our TestFlight submission could be reviewed first. We would also love to hear from other developers who have experienced similar TestFlight review delays. How long did your review take, and was there anything that helped move the process forward? Thank you all for your time and support.

Hello Apple Developer Community, I am reaching out regarding an unusually long App Store review delay affecting our application, MatchMate: Sports Community. Our first iOS release (version 1.0, build 45) was submitted on September 28, 2026, and as of October 19, it has remained in "Waiting for Review" for 21 days, without any progress or explanation. Apple states that 90% of submissions are reviewed within 48 hours. I understand that certain applications may require additional time, but three weeks without any update is extremely concerning. I have already contacted Apple Developer Support to request clarification, but unfortunately, I have not received a response. As an independent developer and co-founder of MatchMate, I have invested significant time and resources into building this application. The delay is directly affecting our planned launch and marketing activities. I would greatly appreciate guidance on the following: Is a 21-day wait normal for a first-time App Store submission? Could this indicate that our submission is stuck in the review queue? Is there an appropriate way to escalate this issue to the App Review team without cancelling and resubmitting the application? If an Apple representative could look into this situation or advise on the appropriate next steps, I would be extremely grateful. Thank you for your time and assistance. Frederico Coelho Co-Founder, MatchMate

I submitted my app for App Review for the first time on October 5, 2026. As of today, October 13, it has been more than a week, and my app is still waiting for review. I have not received any updates or information about the status of my submission. I have also contacted Apple via email to ask about the delay, but I have not received any response. I understand that the App Review process can take time, but since this is my first submission, I am concerned about the prolonged wait and lack of communication. Has anyone experienced a similar delay with their first app submission recently? Is there any recommended way to contact the App Review team and get an update? I would appreciate any advice or guidance.

Hello, My app Barangoló (Apple ID: 6815393371, iOS) was submitted for review on Oct 18 and has been in "Waiting for Review" for 10 days. I submitted an expedited review request on Oct 25 but have not received any response or status change yet. Submission date: Oct, 18 at 1:29 AM Expedite request: submitted Oct 25, no reply Messages in Resolution Center / email: none Review notes: filled in Is there anything that could be blocking the review, or is this a queue issue? Could someone from App Review please take a look? Thank you, Tamás Ali